Repository navigation
Make CLI-only installation onboarding operational - #30
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make the currently supported CLI-only installation path operational when
WEB_ENABLED=false: the App’s/dashboardinstallation landing redirects through the existing safe response helper to the canonical public setup landing. Ignore untrusted installation/redirect query values. OAuth routes and all dashboard mutations remain disabled; no website client or session key is provisioned.Update the README/installation guide to make CLI onboarding primary, remove the obsolete real workflow SHA from setup commands, and distinguish verified native verdict/autonomous-merge evidence from pending live acceptance. Website OAuth is an explicitly deferred enhancement, not a current release blocker. No feature gate, secret, credential, quota or merge policy is changed.
Validation: Node 24 full check (196 tests on this branch), including the installation redirect with a malicious
nextvalue and retained 503 responses for disabled OAuth and mutation routes. Full GitHub CI required before the authorized normal merge/deployment. Backend-only change; retain the synchronized immutable runner pin.